Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef7519ffb314fe2da264cd4785f822940b30ec795d81e34a7527b753efcf5dfd

Tx prefix hash: 4b9e3c74aeb00ba3edc9363e53bd5c42f820b1db668ca50847716a0f4677d147
Tx public key: 171e3fbd67e191fca23031a0f20a47d4fb50941a5c4efd49a97b65067e3375c0
Timestamp: 1657086183 Timestamp [UCT]: 2022-07-06 05:43:03 Age [y:d:h:m:s]: 03:117:18:12:10
Block: 537668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 863891 RingCT/type: yes/0
Extra: 01171e3fbd67e191fca23031a0f20a47d4fb50941a5c4efd49a97b65067e3375c0021100000001e6d27f9c000000000000000000

1 output(s) for total of 10.150393287000 dcy

stealth address amount amount idx
00: 66013eb54b322e265caaaa90279799cfac8cdb3855e73aa34cdde279c3b028bf 10.150393287000 967579 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": 537678, "vin": [ { "gen": { "height": 537668 } } ], "vout": [ { "amount": 10150393287, "target": { "key": "66013eb54b322e265caaaa90279799cfac8cdb3855e73aa34cdde279c3b028bf" } } ], "extra": [ 1, 23, 30, 63, 189, 103, 225, 145, 252, 162, 48, 49, 160, 242, 10, 71, 212, 251, 80, 148, 26, 92, 78, 253, 73, 169, 123, 101, 6, 126, 51, 117, 192, 2, 17, 0, 0, 0, 1, 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