Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b37cd89195f96c41ff6e03ad967a8a699a29db51db37c39d54611a73c4877b7

Tx prefix hash: ac3eaac6105108cb6f510b3d832c7d0e8bf356b451bdcb791083a8904365ee56
Tx public key: efb8af4e6550d656d9e3ccb10162980f8333b8bae4d093b1886ed7430528d068
Timestamp: 1732690463 Timestamp [UCT]: 2024-11-27 06:54:23 Age [y:d:h:m:s]: 00:111:03:05:15
Block: 1162664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79243 RingCT/type: yes/0
Extra: 01efb8af4e6550d656d9e3ccb10162980f8333b8bae4d093b1886ed7430528d0680211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44176f62a61e6bc6d91f1f9fd8baabe775b51120ee3e6930c2f3a28d65b7aa92 0.600000000000 1648321 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": 1162674, "vin": [ { "gen": { "height": 1162664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44176f62a61e6bc6d91f1f9fd8baabe775b51120ee3e6930c2f3a28d65b7aa92" } } ], "extra": [ 1, 239, 184, 175, 78, 101, 80, 214, 86, 217, 227, 204, 177, 1, 98, 152, 15, 131, 51, 184, 186, 228, 208, 147, 177, 136, 110, 215, 67, 5, 40, 208, 104, 2, 17, 0, 0, 0, 5, 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