Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7db5aeb15ca03835df55778e48f4354011fc1ff407142f70a9ecc30cf2e580d

Tx prefix hash: 8c51b965208f4f7181bebc3dac4c909a4d59259e4dc0a761f76d1e9317ce224b
Tx public key: 0c82ac0bd3944de8e45d93b953976af69abc44dc1c07d7c0c501342181836c3f
Timestamp: 1700474769 Timestamp [UCT]: 2023-11-20 10:06:09 Age [y:d:h:m:s]: 00:359:23:46:00
Block: 895685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257761 RingCT/type: yes/0
Extra: 010c82ac0bd3944de8e45d93b953976af69abc44dc1c07d7c0c501342181836c3f0211000000014b8f5122000000000000000000

1 output(s) for total of 0.661033955000 dcy

stealth address amount amount idx
00: 8670f53538bbc7184cf5bfc05744b5d6f3393aad41675bf3780195020c51efc6 0.661033955000 1351926 of 0

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": 895695, "vin": [ { "gen": { "height": 895685 } } ], "vout": [ { "amount": 661033955, "target": { "key": "8670f53538bbc7184cf5bfc05744b5d6f3393aad41675bf3780195020c51efc6" } } ], "extra": [ 1, 12, 130, 172, 11, 211, 148, 77, 232, 228, 93, 147, 185, 83, 151, 106, 246, 154, 188, 68, 220, 28, 7, 215, 192, 197, 1, 52, 33, 129, 131, 108, 63, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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