Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e6a262615e659a3164b1e7d610b95085ee4654ddeb220d37fb16719015e3de3

Tx prefix hash: b10ac8383bb843012df7d2701ebd9bb9634b526dce69f666dc3cff53841683a7
Tx public key: d3f6b044433c426ab04d7894352de2062b3c4cd3ac7da5a3c6d92c9a3267f810
Timestamp: 1732532995 Timestamp [UCT]: 2024-11-25 11:09:55 Age [y:d:h:m:s]: 00:179:19:03:16
Block: 1161359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128359 RingCT/type: yes/0
Extra: 01d3f6b044433c426ab04d7894352de2062b3c4cd3ac7da5a3c6d92c9a3267f8100211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 798530c83c1d7f484cdfa52c1c4b1956a7d9a6df92a8447c0ee3dae14c17bcdc 0.600000000000 1647012 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": 1161369, "vin": [ { "gen": { "height": 1161359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "798530c83c1d7f484cdfa52c1c4b1956a7d9a6df92a8447c0ee3dae14c17bcdc" } } ], "extra": [ 1, 211, 246, 176, 68, 67, 60, 66, 106, 176, 77, 120, 148, 53, 45, 226, 6, 43, 60, 76, 211, 172, 125, 165, 163, 198, 217, 44, 154, 50, 103, 248, 16, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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