Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7293701e90194a0879ce4305b18b51b93a6a8ae0bc5b064df300ce10d73acd2e

Tx prefix hash: 9bdd98835729d2e22aa558c6212892a881100c45b0abc6532e1514ee602456ae
Tx public key: a4a9838126f05e29f5b4c6437e5e92b48acc590afb4e36211687870d9ac468e0
Timestamp: 1699685568 Timestamp [UCT]: 2023-11-11 06:52:48 Age [y:d:h:m:s]: 01:139:11:30:46
Block: 889140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360873 RingCT/type: yes/0
Extra: 01a4a9838126f05e29f5b4c6437e5e92b48acc590afb4e36211687870d9ac468e0021100000006faf35c9c000000000000000000

1 output(s) for total of 0.694880428000 dcy

stealth address amount amount idx
00: 4a22d425935555b6e2211a7361458f8a4d622825603c438b28d3cf3ebcd768dc 0.694880428000 1345117 of 0

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": 889150, "vin": [ { "gen": { "height": 889140 } } ], "vout": [ { "amount": 694880428, "target": { "key": "4a22d425935555b6e2211a7361458f8a4d622825603c438b28d3cf3ebcd768dc" } } ], "extra": [ 1, 164, 169, 131, 129, 38, 240, 94, 41, 245, 180, 198, 67, 126, 94, 146, 180, 138, 204, 89, 10, 251, 78, 54, 33, 22, 135, 135, 13, 154, 196, 104, 224, 2, 17, 0, 0, 0, 6, 250, 243, 92, 156, 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