Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ec12c91849480a90bce72c7c9ec2468b57c247a06fa8c6f1ea58cbf4d22bae0

Tx prefix hash: 650e3d1206d3d480fcc85c81e9dabc0a1f6118f218a66b775968e787ccbae9d3
Tx public key: b184a4cd7e8fb3523592edb3b745e8af1ebc6c208741df6abc47ab7e118c0a3a
Timestamp: 1730643097 Timestamp [UCT]: 2024-11-03 14:11:37 Age [y:d:h:m:s]: 00:142:09:59:56
Block: 1145721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101589 RingCT/type: yes/0
Extra: 01b184a4cd7e8fb3523592edb3b745e8af1ebc6c208741df6abc47ab7e118c0a3a02110000002c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b01eefe52d8674651d97913de4849579e133038da403c4e205f0ec09dc16c7e 0.600000000000 1630214 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": 1145731, "vin": [ { "gen": { "height": 1145721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b01eefe52d8674651d97913de4849579e133038da403c4e205f0ec09dc16c7e" } } ], "extra": [ 1, 177, 132, 164, 205, 126, 143, 179, 82, 53, 146, 237, 179, 183, 69, 232, 175, 30, 188, 108, 32, 135, 65, 223, 106, 188, 71, 171, 126, 17, 140, 10, 58, 2, 17, 0, 0, 0, 44, 31, 10, 83, 235, 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