Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d3ff5530f2efe4a940eed7cb846287fb26cd3e0f634acd6895330ef4fb75da8

Tx prefix hash: 14a61529809913f8af60e6847519556bb1242bca4d60b0d158f81d0628b77235
Tx public key: 8060cdd4175dd4e6210ab624a0fe09f711d674e0f0c5b159109a70cff3360e6b
Timestamp: 1728755531 Timestamp [UCT]: 2024-10-12 17:52:11 Age [y:d:h:m:s]: 00:157:17:39:31
Block: 1130146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112526 RingCT/type: yes/0
Extra: 018060cdd4175dd4e6210ab624a0fe09f711d674e0f0c5b159109a70cff3360e6b02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f823f211dc29bf50eec79aabb299a0406e9f1266010b488bd8a16a2dc719a750 0.600000000000 1613019 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": 1130156, "vin": [ { "gen": { "height": 1130146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f823f211dc29bf50eec79aabb299a0406e9f1266010b488bd8a16a2dc719a750" } } ], "extra": [ 1, 128, 96, 205, 212, 23, 93, 212, 230, 33, 10, 182, 36, 160, 254, 9, 247, 17, 214, 116, 224, 240, 197, 177, 89, 16, 154, 112, 207, 243, 54, 14, 107, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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