Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 327aa9582d636cf24624c00f8c71cf7c532bf8975cb4f1f205021e875f83896a

Tx prefix hash: 4f359b5c371165495cd7c35177fcbcb911d2439c55cbc3bd50b3ab9baf5d7bae
Tx public key: c8d201e8a6de3fffa8ba2ce9fd1fb553d92f41d40387344b1329823251e35436
Timestamp: 1720792738 Timestamp [UCT]: 2024-07-12 13:58:58 Age [y:d:h:m:s]: 00:307:05:17:45
Block: 1064137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219514 RingCT/type: yes/0
Extra: 01c8d201e8a6de3fffa8ba2ce9fd1fb553d92f41d40387344b1329823251e3543602110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbdfc98cff9971e81800f5811cc9345477e59d0f5b6ad4e4e33bb549261edde9 0.600000000000 1534660 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": 1064147, "vin": [ { "gen": { "height": 1064137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbdfc98cff9971e81800f5811cc9345477e59d0f5b6ad4e4e33bb549261edde9" } } ], "extra": [ 1, 200, 210, 1, 232, 166, 222, 63, 255, 168, 186, 44, 233, 253, 31, 181, 83, 217, 47, 65, 212, 3, 135, 52, 75, 19, 41, 130, 50, 81, 227, 84, 54, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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