Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 48c0ccd1d7207ae2ba9038dd1ee6b698ebd3afff9983ed27bb03522ebbfcdcde

Tx prefix hash: fbd8548e9a2525058ea4ade3ee185894c2d4f37c215cac0af6454f2aba0994ef
Tx public key: aa7fdab487a7969f7919f957a17f2ae067a5b2c1eec32164b8c3fa120972a0b5
Timestamp: 1576992406 Timestamp [UCT]: 2019-12-22 05:26:46 Age [y:d:h:m:s]: 05:051:20:40:48
Block: 29475 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186427 RingCT/type: yes/0
Extra: 01aa7fdab487a7969f7919f957a17f2ae067a5b2c1eec32164b8c3fa120972a0b50211000000254943cd9f000000000000000000

1 output(s) for total of 490.160096019000 dcy

stealth address amount amount idx
00: 391bc46e4804c7fd4031cb564699dce7e94c5c6fe8251151ccfa2e6d0262a858 490.160096019000 48511 of 0

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": 29485, "vin": [ { "gen": { "height": 29475 } } ], "vout": [ { "amount": 490160096019, "target": { "key": "391bc46e4804c7fd4031cb564699dce7e94c5c6fe8251151ccfa2e6d0262a858" } } ], "extra": [ 1, 170, 127, 218, 180, 135, 167, 150, 159, 121, 25, 249, 87, 161, 127, 42, 224, 103, 165, 178, 193, 238, 195, 33, 100, 184, 195, 250, 18, 9, 114, 160, 181, 2, 17, 0, 0, 0, 37, 73, 67, 205, 159, 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