Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 229d9d410924684c0a1ddb90c7dca18a89b0d45029c85ec5be9f6e08759123ef

Tx prefix hash: 0cd8742189d8eab20a7cb90391ee33a7a7580c68e09eea14b142e345e2684f06
Tx public key: de151bac2b74abe1ad1fd1db1431ffb9b95e1304aaebbfb7c2fc037d6030e509
Timestamp: 1715490488 Timestamp [UCT]: 2024-05-12 05:08:08 Age [y:d:h:m:s]: 01:035:11:59:07
Block: 1020204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286177 RingCT/type: yes/0
Extra: 01de151bac2b74abe1ad1fd1db1431ffb9b95e1304aaebbfb7c2fc037d6030e50902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4307aa2c6766bb489d6a7a74503b95d68669f3df6666f56cf99b6007ae66a34 0.600000000000 1484265 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": 1020214, "vin": [ { "gen": { "height": 1020204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4307aa2c6766bb489d6a7a74503b95d68669f3df6666f56cf99b6007ae66a34" } } ], "extra": [ 1, 222, 21, 27, 172, 43, 116, 171, 225, 173, 31, 209, 219, 20, 49, 255, 185, 185, 94, 19, 4, 170, 235, 191, 183, 194, 252, 3, 125, 96, 48, 229, 9, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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