Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b8310d58cc1a90123a2dd7e89bfeaf449333c4245022f70e084d063b21991edb

Tx prefix hash: 61f58b3ccd1eccb2d23e7fa6ad4dc0de6b8d4a5d85194ba9a3eb9cda627e6ddb
Tx public key: faffe8f45ece4be310b842318160fb8074715f235b53fd782a8ab8a7db5350c0
Timestamp: 1713127615 Timestamp [UCT]: 2024-04-14 20:46:55 Age [y:d:h:m:s]: 01:002:09:27:45
Block: 1000563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262673 RingCT/type: yes/0
Extra: 01faffe8f45ece4be310b842318160fb8074715f235b53fd782a8ab8a7db5350c002110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be2095789e8076f6d5010a8f9345abd8a340a7e7a125febca64cf98cff43c2d8 0.600000000000 1461061 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1000573, "vin": [ { "gen": { "height": 1000563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be2095789e8076f6d5010a8f9345abd8a340a7e7a125febca64cf98cff43c2d8" } } ], "extra": [ 1, 250, 255, 232, 244, 94, 206, 75, 227, 16, 184, 66, 49, 129, 96, 251, 128, 116, 113, 95, 35, 91, 83, 253, 120, 42, 138, 184, 167, 219, 83, 80, 192, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8