Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d110bb4994aef290fad7046edc132a1991d53cc38a2cd16e2e1908e545147033

Tx prefix hash: 349ac1f89d256a0bd8f8f99e721685a21cb0793f73976615256634fb7ac53b08
Tx public key: 6470eff6c2d7f427bbba5d8aaf310b3c06da41e13bafd7d5a7a6a0328638f78b
Timestamp: 1657879784 Timestamp [UCT]: 2022-07-15 10:09:44 Age [y:d:h:m:s]: 02:262:12:20:58
Block: 544212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 708771 RingCT/type: yes/0
Extra: 016470eff6c2d7f427bbba5d8aaf310b3c06da41e13bafd7d5a7a6a0328638f78b021100000015e6d27f9c000000000000000000

1 output(s) for total of 9.656058131000 dcy

stealth address amount amount idx
00: 56f35c04772bafde7f84a817fe62de537533c17acaab8f3ff341194453359999 9.656058131000 974967 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": 544222, "vin": [ { "gen": { "height": 544212 } } ], "vout": [ { "amount": 9656058131, "target": { "key": "56f35c04772bafde7f84a817fe62de537533c17acaab8f3ff341194453359999" } } ], "extra": [ 1, 100, 112, 239, 246, 194, 215, 244, 39, 187, 186, 93, 138, 175, 49, 11, 60, 6, 218, 65, 225, 59, 175, 215, 213, 167, 166, 160, 50, 134, 56, 247, 139, 2, 17, 0, 0, 0, 21, 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