Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01f4b73f0ba144491546b3447892dbd9f48e71911bf52a503ec24baa323cec78

Tx prefix hash: 43d2082a76c0fe9f11309ac46e6e4b2bf62d96dd3c18ea372830450369cc4f28
Tx public key: 4b7f64ee15f3013d337c1c602aea7a17df54b240c165dac4ec82bcd5b18dbb53
Timestamp: 1709077574 Timestamp [UCT]: 2024-02-27 23:46:14 Age [y:d:h:m:s]: 01:113:17:58:48
Block: 967003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342198 RingCT/type: yes/0
Extra: 014b7f64ee15f3013d337c1c602aea7a17df54b240c165dac4ec82bcd5b18dbb5302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22f2f768b489f2d5bbe3eb56132de052fbeba4123d4fb7c6741128bf30a4d7f9 0.600000000000 1426774 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": 967013, "vin": [ { "gen": { "height": 967003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22f2f768b489f2d5bbe3eb56132de052fbeba4123d4fb7c6741128bf30a4d7f9" } } ], "extra": [ 1, 75, 127, 100, 238, 21, 243, 1, 61, 51, 124, 28, 96, 42, 234, 122, 23, 223, 84, 178, 64, 193, 101, 218, 196, 236, 130, 188, 213, 177, 141, 187, 83, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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