Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0bbc8333cb4e6f26c931cba1cf53da3fdf91b44bc2f2e17eecd0d03bfe1145d7

Tx prefix hash: 2723e3014d7ac00a6a52c0566902e66025a83897a400082909acd44760cae5b3
Tx public key: 395dcd10872ca66bf0c693d982adc9cf427a2900d032e78c984528520e8c8a20
Timestamp: 1712156965 Timestamp [UCT]: 2024-04-03 15:09:25 Age [y:d:h:m:s]: 01:245:04:45:24
Block: 992508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433993 RingCT/type: yes/0
Extra: 01395dcd10872ca66bf0c693d982adc9cf427a2900d032e78c984528520e8c8a200211000000023f82f9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 151ce186e3bb4bd20b1fa9798ee2b2ba1b8ee41fdae305f44a8358d445027188 0.600000000000 1452850 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": 992518, "vin": [ { "gen": { "height": 992508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "151ce186e3bb4bd20b1fa9798ee2b2ba1b8ee41fdae305f44a8358d445027188" } } ], "extra": [ 1, 57, 93, 205, 16, 135, 44, 166, 107, 240, 198, 147, 217, 130, 173, 201, 207, 66, 122, 41, 0, 208, 50, 231, 140, 152, 69, 40, 82, 14, 140, 138, 32, 2, 17, 0, 0, 0, 2, 63, 130, 249, 251, 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