Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61101dc8d5e4de490c884b5d69b756a9f20cb447d94e86406f3cf25065149a6e

Tx prefix hash: 9f3074c30736561e7ecd6ff3f7d1f74f7c2efcd7ef3ac61be8c16bb3afd6d4f1
Tx public key: 02d4e0ddaf7d74e75e72d63aeeba31e504fc08b1897b394544ae4990ac150d2c
Timestamp: 1699430751 Timestamp [UCT]: 2023-11-08 08:05:51 Age [y:d:h:m:s]: 01:142:10:35:54
Block: 887024 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362995 RingCT/type: yes/0
Extra: 0102d4e0ddaf7d74e75e72d63aeeba31e504fc08b1897b394544ae4990ac150d2c02110000000475e3f0e9000000000000000000

1 output(s) for total of 0.706189522000 dcy

stealth address amount amount idx
00: df5c8c7f6c47338201d6e42268bdb2056b11aa9211f1223a4dbb41975afda5e7 0.706189522000 1342875 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": 887034, "vin": [ { "gen": { "height": 887024 } } ], "vout": [ { "amount": 706189522, "target": { "key": "df5c8c7f6c47338201d6e42268bdb2056b11aa9211f1223a4dbb41975afda5e7" } } ], "extra": [ 1, 2, 212, 224, 221, 175, 125, 116, 231, 94, 114, 214, 58, 238, 186, 49, 229, 4, 252, 8, 177, 137, 123, 57, 69, 68, 174, 73, 144, 172, 21, 13, 44, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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