Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9648f9195063ded2e0feb1f1374da157902eb09a6c8bc3ccaaec40ce2de7fa3d

Tx prefix hash: 4115da0b5540fe06906cb2cf22d72dff0e116f60ebbfac8b574975288b187215
Tx public key: 02e2e9081ca50972caffd92b853619a0d0adbe2dfc47aeae7bd80246f48da80c
Timestamp: 1714254191 Timestamp [UCT]: 2024-04-27 21:43:11 Age [y:d:h:m:s]: 00:253:16:14:23
Block: 1009914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181588 RingCT/type: yes/0
Extra: 0102e2e9081ca50972caffd92b853619a0d0adbe2dfc47aeae7bd80246f48da80c0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2a0c773c3ee7a1421d40fe340573c1c08291f9ff367d302622415c2acda5d38 0.600000000000 1471720 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": 1009924, "vin": [ { "gen": { "height": 1009914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2a0c773c3ee7a1421d40fe340573c1c08291f9ff367d302622415c2acda5d38" } } ], "extra": [ 1, 2, 226, 233, 8, 28, 165, 9, 114, 202, 255, 217, 43, 133, 54, 25, 160, 208, 173, 190, 45, 252, 71, 174, 174, 123, 216, 2, 70, 244, 141, 168, 12, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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