Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f3dad59f0dfdcdb83a1c635712a2411a412c4420f59be0034b4c631346084cc

Tx prefix hash: 25d624856dfc2afc15cbf9eeb480f7a21c2ffb832d3cb66e5b32040ae52d2ff0
Tx public key: 2f5e3a72c95ca8d5fc308e5abafc98db858b20de7b1bf69c272a5f794187b55a
Timestamp: 1686365164 Timestamp [UCT]: 2023-06-10 02:46:04 Age [y:d:h:m:s]: 02:197:01:57:08
Block: 778955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 660679 RingCT/type: yes/0
Extra: 012f5e3a72c95ca8d5fc308e5abafc98db858b20de7b1bf69c272a5f794187b55a021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.610641504000 dcy

stealth address amount amount idx
00: 5f2646d9c947d0d37bc0d3432d2ec4069e8e8ba2914e6af2b0ecb35d4f9dc1b6 1.610641504000 1228598 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": 778965, "vin": [ { "gen": { "height": 778955 } } ], "vout": [ { "amount": 1610641504, "target": { "key": "5f2646d9c947d0d37bc0d3432d2ec4069e8e8ba2914e6af2b0ecb35d4f9dc1b6" } } ], "extra": [ 1, 47, 94, 58, 114, 201, 92, 168, 213, 252, 48, 142, 90, 186, 252, 152, 219, 133, 139, 32, 222, 123, 27, 246, 156, 39, 42, 95, 121, 65, 135, 181, 90, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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