Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bf3c953d18d1db186556f23edad4eb939cd52c5a9fae8fcb0eff1e68a8167eb

Tx prefix hash: 7aba556c26f0ef3fc12c87602d269df0fe940a115c54112697bb1ed51f9e634a
Tx public key: 1ee1d91243641d4961a6e04c7ab624370f002a2731e6ef2b6ef3e71b6ae13824
Timestamp: 1726470242 Timestamp [UCT]: 2024-09-16 07:04:02 Age [y:d:h:m:s]: 00:241:14:49:04
Block: 1111188 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172542 RingCT/type: yes/0
Extra: 011ee1d91243641d4961a6e04c7ab624370f002a2731e6ef2b6ef3e71b6ae13824021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64b91210af512f69363315395d696d55c952a6b4e2e74f771c5bd1222e511056 0.600000000000 1590063 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": 1111198, "vin": [ { "gen": { "height": 1111188 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64b91210af512f69363315395d696d55c952a6b4e2e74f771c5bd1222e511056" } } ], "extra": [ 1, 30, 225, 217, 18, 67, 100, 29, 73, 97, 166, 224, 76, 122, 182, 36, 55, 15, 0, 42, 39, 49, 230, 239, 43, 110, 243, 231, 27, 106, 225, 56, 36, 2, 17, 0, 0, 0, 3, 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