Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82f810531cc4a75b7f4e7626e4c510024c580b4b63ca74e8063881209df9f1a2

Tx prefix hash: a764c2af2e920a7d059761cfbfbad47c63883d3abbcb0cdfc2248dbb96fe14ea
Tx public key: 3cfcbb68f12dd5d11eaaac768e9ec09f125b081c7877c0823d799f64f5edda27
Timestamp: 1715296780 Timestamp [UCT]: 2024-05-09 23:19:40 Age [y:d:h:m:s]: 00:355:09:41:41
Block: 1018558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254087 RingCT/type: yes/0
Extra: 013cfcbb68f12dd5d11eaaac768e9ec09f125b081c7877c0823d799f64f5edda270211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d158703d3826a3a0e3dc18d46dfba79796600181f2bc00bd5ceaa8e1df27f08d 0.600000000000 1482351 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": 1018568, "vin": [ { "gen": { "height": 1018558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d158703d3826a3a0e3dc18d46dfba79796600181f2bc00bd5ceaa8e1df27f08d" } } ], "extra": [ 1, 60, 252, 187, 104, 241, 45, 213, 209, 30, 170, 172, 118, 142, 158, 192, 159, 18, 91, 8, 28, 120, 119, 192, 130, 61, 121, 159, 100, 245, 237, 218, 39, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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