Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bee2ac5848426eb27f05479cc9184b4c8d3b7a4c08607fb98d366067109c68b8

Tx prefix hash: 16232a94b30cad8f26893d6a2cf2a7973c7e3cca64c5c0ad5fd86f9319a46ace
Tx public key: 90d6b76b90c9f4dc43af813a358a72f3200fbdcc78c82c307f795d6355ed2da7
Timestamp: 1702128853 Timestamp [UCT]: 2023-12-09 13:34:13 Age [y:d:h:m:s]: 01:189:23:18:45
Block: 909386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396865 RingCT/type: yes/0
Extra: 0190d6b76b90c9f4dc43af813a358a72f3200fbdcc78c82c307f795d6355ed2da702110000000833af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0df134536b38307eaa4bc472e45f42ca9f4f84069e0adef4f301f7373fac8093 0.600000000000 1366471 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": 909396, "vin": [ { "gen": { "height": 909386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0df134536b38307eaa4bc472e45f42ca9f4f84069e0adef4f301f7373fac8093" } } ], "extra": [ 1, 144, 214, 183, 107, 144, 201, 244, 220, 67, 175, 129, 58, 53, 138, 114, 243, 32, 15, 189, 204, 120, 200, 44, 48, 127, 121, 93, 99, 85, 237, 45, 167, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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