Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50f7e084cea766ceb1aecc4664a9119bbd1412b4ac405ce6067c9a6f3f181365

Tx prefix hash: 2cfbe9c153f9f5ab282ea893b7453f238852fabf7ad21975fa0da12a564e6b02
Tx public key: c7383ed9d4446db1e92b04d1936f60ea37fc7c81988fc0512c03222aa6f4138f
Timestamp: 1707471198 Timestamp [UCT]: 2024-02-09 09:33:18 Age [y:d:h:m:s]: 01:273:02:42:13
Block: 953680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453955 RingCT/type: yes/0
Extra: 01c7383ed9d4446db1e92b04d1936f60ea37fc7c81988fc0512c03222aa6f4138f02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a7cbe0e166a480c2df80fc2c9a87d0cbdc04bf7af93a26f2ee95d156474e7aa 0.600000000000 1412918 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": 953690, "vin": [ { "gen": { "height": 953680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a7cbe0e166a480c2df80fc2c9a87d0cbdc04bf7af93a26f2ee95d156474e7aa" } } ], "extra": [ 1, 199, 56, 62, 217, 212, 68, 109, 177, 233, 43, 4, 209, 147, 111, 96, 234, 55, 252, 124, 129, 152, 143, 192, 81, 44, 3, 34, 42, 166, 244, 19, 143, 2, 17, 0, 0, 0, 7, 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