Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 507f836c9a952a26fd294b5d0267ab87032fb79d3d678220506bdd3cf4c76e5d

Tx prefix hash: 8445df71df383b87a5a89b8c882adb551126d30065605cacba768fb983773320
Tx public key: f56046dd611743a957134a36c6f326c92282a97c39ea9867c6a876fa16931e37
Timestamp: 1706153979 Timestamp [UCT]: 2024-01-25 03:39:39 Age [y:d:h:m:s]: 01:140:06:03:14
Block: 942741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361314 RingCT/type: yes/0
Extra: 01f56046dd611743a957134a36c6f326c92282a97c39ea9867c6a876fa16931e3702110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57f18e0c9538af04dc27c71721edb3a464037951c3d7df6e8c8bbae510e9eb65 0.600000000000 1400917 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": 942751, "vin": [ { "gen": { "height": 942741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57f18e0c9538af04dc27c71721edb3a464037951c3d7df6e8c8bbae510e9eb65" } } ], "extra": [ 1, 245, 96, 70, 221, 97, 23, 67, 169, 87, 19, 74, 54, 198, 243, 38, 201, 34, 130, 169, 124, 57, 234, 152, 103, 198, 168, 118, 250, 22, 147, 30, 55, 2, 17, 0, 0, 0, 4, 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