Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e995e9179ae4ace2393afe9eed934821cdab4bbfe5f3e044b22894e04b7c2b84

Tx prefix hash: 3fbb095554a22f82b6f64987125f659d11b3cdc938da20ee4eed63f2a5ef8bb4
Tx public key: 8fd2025f7b02af7dc7f70548f3212d016eba908de8eecd4d1ff14cdca985220d
Timestamp: 1741340871 Timestamp [UCT]: 2025-03-07 09:47:51 Age [y:d:h:m:s]: 00:324:01:24:20
Block: 1234024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229245 RingCT/type: yes/0
Extra: 018fd2025f7b02af7dc7f70548f3212d016eba908de8eecd4d1ff14cdca985220d021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae0308811df281a6a22c3a0cd4cfb722071d0c050269df25ccd55c646c9a8e4f 0.600000000000 1720949 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": 1234034, "vin": [ { "gen": { "height": 1234024 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae0308811df281a6a22c3a0cd4cfb722071d0c050269df25ccd55c646c9a8e4f" } } ], "extra": [ 1, 143, 210, 2, 95, 123, 2, 175, 125, 199, 247, 5, 72, 243, 33, 45, 1, 110, 186, 144, 141, 232, 238, 205, 77, 31, 241, 76, 220, 169, 133, 34, 13, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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