Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9c31997eae9cc3ba50df19443cc9fc25c67abd410e8cbfe21fd22477656dd47

Tx prefix hash: 693dcb9a7d1e9afd4027555c958027ce8c2f4b9aceec52d197e33be218b9c055
Tx public key: 68e48c2936609feeac90f026862bf9e5d7621374969609d171a6209ee90f2e9a
Timestamp: 1703938713 Timestamp [UCT]: 2023-12-30 12:18:33 Age [y:d:h:m:s]: 01:032:22:18:59
Block: 924399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284616 RingCT/type: yes/0
Extra: 0168e48c2936609feeac90f026862bf9e5d7621374969609d171a6209ee90f2e9a0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8fe6ea6050150aadd0dc7a4ea1d0d760036a07a3dbcc9cd3fd0efb88a90afee3 0.600000000000 1382147 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": 924409, "vin": [ { "gen": { "height": 924399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8fe6ea6050150aadd0dc7a4ea1d0d760036a07a3dbcc9cd3fd0efb88a90afee3" } } ], "extra": [ 1, 104, 228, 140, 41, 54, 96, 159, 238, 172, 144, 240, 38, 134, 43, 249, 229, 215, 98, 19, 116, 150, 150, 9, 209, 113, 166, 32, 158, 233, 15, 46, 154, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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