Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28debad81935669a4daf20a2cad0167d86632ed637581f3a295757457c75bcef

Tx prefix hash: aeb26b1f661de54cbfec88e783c882f394530e4f4d8fb66fefd0f67c31a8d9bd
Tx public key: 922c26b3f1acda6a60da4c10fd84c76770095ca7d3bf00792be9e209bbca5de9
Timestamp: 1717024147 Timestamp [UCT]: 2024-05-29 23:09:07 Age [y:d:h:m:s]: 00:154:14:20:59
Block: 1032889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110666 RingCT/type: yes/0
Extra: 01922c26b3f1acda6a60da4c10fd84c76770095ca7d3bf00792be9e209bbca5de90211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c94a69b42696815e35783bb25c1a0f26962dc91e8e1a6f77bcc454abfc7e05ac 0.600000000000 1501344 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": 1032899, "vin": [ { "gen": { "height": 1032889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c94a69b42696815e35783bb25c1a0f26962dc91e8e1a6f77bcc454abfc7e05ac" } } ], "extra": [ 1, 146, 44, 38, 179, 241, 172, 218, 106, 96, 218, 76, 16, 253, 132, 199, 103, 112, 9, 92, 167, 211, 191, 0, 121, 43, 233, 226, 9, 187, 202, 93, 233, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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