Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 486321634d19bad9d53b920972501dab97a38729ac3c872b9a17e16a4e73adb2

Tx prefix hash: 881a1141441013a125718745963d5b7d3c3fb2eb079a6462d63bdee2d40350e2
Tx public key: 4c5fdc51a29486f8397765a303a2dd8d88c8a3af1a156e75599ff447b6fb2757
Timestamp: 1741437316 Timestamp [UCT]: 2025-03-08 12:35:16 Age [y:d:h:m:s]: 00:251:12:11:26
Block: 1234829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177483 RingCT/type: yes/0
Extra: 014c5fdc51a29486f8397765a303a2dd8d88c8a3af1a156e75599ff447b6fb2757021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef1c34102b535646469089d915d728f87d5e46b4dd43899d32396230957099cb 0.600000000000 1721764 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": 1234839, "vin": [ { "gen": { "height": 1234829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef1c34102b535646469089d915d728f87d5e46b4dd43899d32396230957099cb" } } ], "extra": [ 1, 76, 95, 220, 81, 162, 148, 134, 248, 57, 119, 101, 163, 3, 162, 221, 141, 136, 200, 163, 175, 26, 21, 110, 117, 89, 159, 244, 71, 182, 251, 39, 87, 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