Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d263a51414a62c6336f0c8006ffba959a6d316fdafc8dc91a51aaa8332eb1d0

Tx prefix hash: 68bf6ae6ba637f9bc119638df8b30559e17d7c21cda004a57b42fecbf9be469d
Tx public key: 370ce373aee05be46a958d4928ccafb5ed0e2b372e5b29595de40b2c20e7a524
Timestamp: 1734134641 Timestamp [UCT]: 2024-12-14 00:04:01 Age [y:d:h:m:s]: 00:100:14:26:34
Block: 1174646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71671 RingCT/type: yes/0
Extra: 01370ce373aee05be46a958d4928ccafb5ed0e2b372e5b29595de40b2c20e7a524021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 461c1a8a6d758822825a008fe5f133266a9482f00fc5188171996b07da46d10f 0.600000000000 1660827 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": 1174656, "vin": [ { "gen": { "height": 1174646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "461c1a8a6d758822825a008fe5f133266a9482f00fc5188171996b07da46d10f" } } ], "extra": [ 1, 55, 12, 227, 115, 174, 224, 91, 228, 106, 149, 141, 73, 40, 204, 175, 181, 237, 14, 43, 55, 46, 91, 41, 89, 93, 228, 11, 44, 32, 231, 165, 36, 2, 17, 0, 0, 0, 3, 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