Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a74e36f1748374114f8ae53b119afff36e15e8150448c4c08a7175f1083d3877

Tx prefix hash: 5889220b7184cb21235d4c66342ac2ceffa845e6bb69851eedb42e681f13444f
Tx public key: e9f29485060c6cc0d1aa6e56d726c5efc50be0322d5b903acbfa4dfec9f4d2c0
Timestamp: 1729149012 Timestamp [UCT]: 2024-10-17 07:10:12 Age [y:d:h:m:s]: 00:241:14:22:28
Block: 1133403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172400 RingCT/type: yes/0
Extra: 01e9f29485060c6cc0d1aa6e56d726c5efc50be0322d5b903acbfa4dfec9f4d2c002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78fb7e7f5aaf09e9498c66ada22c2c4063543951c875fc09378ce93da819c3bd 0.600000000000 1616516 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": 1133413, "vin": [ { "gen": { "height": 1133403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78fb7e7f5aaf09e9498c66ada22c2c4063543951c875fc09378ce93da819c3bd" } } ], "extra": [ 1, 233, 242, 148, 133, 6, 12, 108, 192, 209, 170, 110, 86, 215, 38, 197, 239, 197, 11, 224, 50, 45, 91, 144, 58, 203, 250, 77, 254, 201, 244, 210, 192, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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