Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d98c7f1d3550617b2d478ecf35f5a607cd0d700ea7808e10a58b8a2ec8a769e4

Tx prefix hash: 43813e238a4e25c4827ebfeca903922f58f0582a448743d8b95c4d7acf304b72
Tx public key: 0e33b01f3f1801380c8ad4eabb343db1ab7711fd2bbe4480dbe4f3c83e62ce77
Timestamp: 1711852144 Timestamp [UCT]: 2024-03-31 02:29:04 Age [y:d:h:m:s]: 00:331:03:25:45
Block: 990019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236715 RingCT/type: yes/0
Extra: 010e33b01f3f1801380c8ad4eabb343db1ab7711fd2bbe4480dbe4f3c83e62ce770211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70063cc7a978b792ec5494467f62e4ac2fb45748707f3ba9a58ab6a36942c13b 0.600000000000 1450339 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": 990029, "vin": [ { "gen": { "height": 990019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70063cc7a978b792ec5494467f62e4ac2fb45748707f3ba9a58ab6a36942c13b" } } ], "extra": [ 1, 14, 51, 176, 31, 63, 24, 1, 56, 12, 138, 212, 234, 187, 52, 61, 177, 171, 119, 17, 253, 43, 190, 68, 128, 219, 228, 243, 200, 62, 98, 206, 119, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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