Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8c4921124800282fe1c5e8d2fdf760c8a96e96885a40323a681763904038030

Tx prefix hash: dccb9bf0faefe2c47b3309bf7807c7a38e373a4836735f63eed7e2cab1b2206d
Tx public key: 6ffb4e22e0440496adc144d1a4b7ca13e0fee1a5f3d30e7e3829c0715a9be0dd
Timestamp: 1727386955 Timestamp [UCT]: 2024-09-26 21:42:35 Age [y:d:h:m:s]: 00:238:23:53:25
Block: 1118798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170660 RingCT/type: yes/0
Extra: 016ffb4e22e0440496adc144d1a4b7ca13e0fee1a5f3d30e7e3829c0715a9be0dd021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d78739dbed1e552a5bdce04b603c227602f54552d619aaa55ba7573166252a4 0.600000000000 1600119 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": 1118808, "vin": [ { "gen": { "height": 1118798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d78739dbed1e552a5bdce04b603c227602f54552d619aaa55ba7573166252a4" } } ], "extra": [ 1, 111, 251, 78, 34, 224, 68, 4, 150, 173, 193, 68, 209, 164, 183, 202, 19, 224, 254, 225, 165, 243, 211, 14, 126, 56, 41, 192, 113, 90, 155, 224, 221, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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