Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb4f00895c92d78d442e2af143801e7ab6273a1890cba4dbd1fa283c75fb7b46

Tx prefix hash: 21e9af6f7bd7b7de3450847ca05a92ed9df623c340a4f5f5e63b4d4ed1758567
Tx public key: f1782f2b4f833cb4dc80f990f879a5bb1d7c80d0abdbe8fd9199369b97aedff6
Timestamp: 1720864229 Timestamp [UCT]: 2024-07-13 09:50:29 Age [y:d:h:m:s]: 00:302:00:56:32
Block: 1064737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215804 RingCT/type: yes/0
Extra: 01f1782f2b4f833cb4dc80f990f879a5bb1d7c80d0abdbe8fd9199369b97aedff6021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6abf15168512448fcf4108298dc0a37e6de147d6a6d18c6cebcf44a9a785a7cf 0.600000000000 1535272 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": 1064747, "vin": [ { "gen": { "height": 1064737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6abf15168512448fcf4108298dc0a37e6de147d6a6d18c6cebcf44a9a785a7cf" } } ], "extra": [ 1, 241, 120, 47, 43, 79, 131, 60, 180, 220, 128, 249, 144, 248, 121, 165, 187, 29, 124, 128, 208, 171, 219, 232, 253, 145, 153, 54, 155, 151, 174, 223, 246, 2, 17, 0, 0, 0, 4, 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