Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f81557f6f448c10df67f5c8bd78ab3543109c9d65c4172ac3488e84d29d424d

Tx prefix hash: 5e725d5e483032337fd64d04664540f1ea2ba0b764847f82cdb0bd62b6ec89ab
Tx public key: cc795872770404c4638c40dc771a1d4cf57ac3f19afa959fc3cbca76c289e1fa
Timestamp: 1737796354 Timestamp [UCT]: 2025-01-25 09:12:34 Age [y:d:h:m:s]: 00:143:08:56:47
Block: 1204899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102212 RingCT/type: yes/0
Extra: 01cc795872770404c4638c40dc771a1d4cf57ac3f19afa959fc3cbca76c289e1fa021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6a0360da14adfa9985e8ff20e2f1109bb535aea90fc368717fa9694c3a8c83e 0.600000000000 1691594 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": 1204909, "vin": [ { "gen": { "height": 1204899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6a0360da14adfa9985e8ff20e2f1109bb535aea90fc368717fa9694c3a8c83e" } } ], "extra": [ 1, 204, 121, 88, 114, 119, 4, 4, 196, 99, 140, 64, 220, 119, 26, 29, 76, 245, 122, 195, 241, 154, 250, 149, 159, 195, 203, 202, 118, 194, 137, 225, 250, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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