Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b078c417c02d030a3bc8217f6585169caa5f414a1fac84e1a9c60ed913cca2d8

Tx prefix hash: 67ad8bea580bc112780159eaef9564539c8af9c4dc608ea3d06a7131f1680b2f
Tx public key: a9a4ff7734adea52e592b9865fe196a5405bed5f0e32793e6b79076bb1f87fd7
Timestamp: 1716087806 Timestamp [UCT]: 2024-05-19 03:03:26 Age [y:d:h:m:s]: 00:190:01:52:22
Block: 1025125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136044 RingCT/type: yes/0
Extra: 01a9a4ff7734adea52e592b9865fe196a5405bed5f0e32793e6b79076bb1f87fd702110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 875e6a72e43cd05efd7f5f49e970a08fbde65f001e118c050a0c3fbb3181a30a 0.600000000000 1491396 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": 1025135, "vin": [ { "gen": { "height": 1025125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "875e6a72e43cd05efd7f5f49e970a08fbde65f001e118c050a0c3fbb3181a30a" } } ], "extra": [ 1, 169, 164, 255, 119, 52, 173, 234, 82, 229, 146, 185, 134, 95, 225, 150, 165, 64, 91, 237, 95, 14, 50, 121, 62, 107, 121, 7, 107, 177, 248, 127, 215, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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