Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f82dc6cb44f126f09014ff746ea6940a391fe7a03eb2a17035b6d6633c3a47f

Tx prefix hash: f67135d950daf6fb3d45a59500a71e9a91006e5df7a4bd6a9d37c506e6bf5661
Tx public key: 850dd3a8c593bdaf21655ff1829a2eb583563c2a7607ee6f01dd3e1ec36308ec
Timestamp: 1743775711 Timestamp [UCT]: 2025-04-04 14:08:31 Age [y:d:h:m:s]: 00:231:10:50:05
Block: 1254173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163145 RingCT/type: yes/0
Extra: 01850dd3a8c593bdaf21655ff1829a2eb583563c2a7607ee6f01dd3e1ec36308ec0211000000024060f6d2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bda4ae4bfa1b708ee69285e3bd7a92598e9b42572236ef3a55e2e4cc1f87f72 0.600000000000 1741254 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": 1254183, "vin": [ { "gen": { "height": 1254173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bda4ae4bfa1b708ee69285e3bd7a92598e9b42572236ef3a55e2e4cc1f87f72" } } ], "extra": [ 1, 133, 13, 211, 168, 197, 147, 189, 175, 33, 101, 95, 241, 130, 154, 46, 181, 131, 86, 60, 42, 118, 7, 238, 111, 1, 221, 62, 30, 195, 99, 8, 236, 2, 17, 0, 0, 0, 2, 64, 96, 246, 210, 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