Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c2760bb3659c45cc93b37ed8c493bd54cb0acbba0ad4e3be99ff07e52caf3c8

Tx prefix hash: e057ba64b7ff2ea67922de443e36a91cc4f9e38f3a806f9a0701dd68de30b9aa
Tx public key: 5f003e2d7a12ccf059bd6e9baeeeddc22b0cf7557b878bc83de435e4d638ab7f
Timestamp: 1743367227 Timestamp [UCT]: 2025-03-30 20:40:27 Age [y:d:h:m:s]: 00:303:03:25:33
Block: 1250787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214303 RingCT/type: yes/0
Extra: 015f003e2d7a12ccf059bd6e9baeeeddc22b0cf7557b878bc83de435e4d638ab7f0211000000021a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45beb39e91e82d0bfd8718c28109d02427c7d69df83a9a9cad29034dba53c89e 0.600000000000 1737840 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": 1250797, "vin": [ { "gen": { "height": 1250787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45beb39e91e82d0bfd8718c28109d02427c7d69df83a9a9cad29034dba53c89e" } } ], "extra": [ 1, 95, 0, 62, 45, 122, 18, 204, 240, 89, 189, 110, 155, 174, 238, 221, 194, 43, 12, 247, 85, 123, 135, 139, 200, 61, 228, 53, 228, 214, 56, 171, 127, 2, 17, 0, 0, 0, 2, 26, 151, 4, 3, 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