Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef60e52a60d00c1ffc1952e0f7bd6c3f37e364690c761f63a8098bd0f0f445b8

Tx prefix hash: 4f83377c71f5ed8db941fb187bccd859f6431c10cf6e7ec44502b60ebe545df2
Tx public key: 7b0f8de02bbf4dd8fcce5cb87bf30793ee1755fb97ff2d1ff119064c9036ac86
Timestamp: 1725642277 Timestamp [UCT]: 2024-09-06 17:04:37 Age [y:d:h:m:s]: 00:190:06:19:10
Block: 1104327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135848 RingCT/type: yes/0
Extra: 017b0f8de02bbf4dd8fcce5cb87bf30793ee1755fb97ff2d1ff119064c9036ac86021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9f52a45500db4483ea7139408d2d9d648697feeb26f404ca24e492f3ed9fd33 0.600000000000 1581428 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": 1104337, "vin": [ { "gen": { "height": 1104327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9f52a45500db4483ea7139408d2d9d648697feeb26f404ca24e492f3ed9fd33" } } ], "extra": [ 1, 123, 15, 141, 224, 43, 191, 77, 216, 252, 206, 92, 184, 123, 243, 7, 147, 238, 23, 85, 251, 151, 255, 45, 31, 241, 25, 6, 76, 144, 54, 172, 134, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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