Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06f8f6d2a44211718166b298cbf34ee6c9599785053d2f6269e61c18dd31b46b

Tx prefix hash: 567d9941bc3e04181a7cf9e015c8e54d06237d05539763d87a25778e23a06a11
Tx public key: 5f7bd5a6feec9649b71f8760f30718e2770bcbe30bb5ac2fe170e1fe70e3212a
Timestamp: 1716301120 Timestamp [UCT]: 2024-05-21 14:18:40 Age [y:d:h:m:s]: 00:163:10:24:58
Block: 1026895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116990 RingCT/type: yes/0
Extra: 015f7bd5a6feec9649b71f8760f30718e2770bcbe30bb5ac2fe170e1fe70e3212a0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f75e9d3f10e69d87f564c5842eeaeea6b9877a21ea98133c4f4038969a9e5cbe 0.600000000000 1494230 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": 1026905, "vin": [ { "gen": { "height": 1026895 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f75e9d3f10e69d87f564c5842eeaeea6b9877a21ea98133c4f4038969a9e5cbe" } } ], "extra": [ 1, 95, 123, 213, 166, 254, 236, 150, 73, 183, 31, 135, 96, 243, 7, 24, 226, 119, 11, 203, 227, 11, 181, 172, 47, 225, 112, 225, 254, 112, 227, 33, 42, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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