Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96b5573536b183840975be6a671d28bc3daa9feaddbfcb2f3f6d543b67ef9c2f

Tx prefix hash: d93a603b2d7b5bfd3ebd8beabc0cec41e2777aa51432ddd6b6229b99df2e6ac2
Tx public key: f266d87848166d8f6e0a0a60f0bce426616fcbb858b1f158c1bcaa1189c2482e
Timestamp: 1675574632 Timestamp [UCT]: 2023-02-05 05:23:52 Age [y:d:h:m:s]: 01:288:02:37:12
Block: 690129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466854 RingCT/type: yes/0
Extra: 01f266d87848166d8f6e0a0a60f0bce426616fcbb858b1f158c1bcaa1189c2482e0211000000027e406890000000000000000000

1 output(s) for total of 3.171875005000 dcy

stealth address amount amount idx
00: 9d108ea11b7d8d2f4e567b55c1d5fb544d8df715d0abab1ccb73847fd767d794 3.171875005000 1132835 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": 690139, "vin": [ { "gen": { "height": 690129 } } ], "vout": [ { "amount": 3171875005, "target": { "key": "9d108ea11b7d8d2f4e567b55c1d5fb544d8df715d0abab1ccb73847fd767d794" } } ], "extra": [ 1, 242, 102, 216, 120, 72, 22, 109, 143, 110, 10, 10, 96, 240, 188, 228, 38, 97, 111, 203, 184, 88, 177, 241, 88, 193, 188, 170, 17, 137, 194, 72, 46, 2, 17, 0, 0, 0, 2, 126, 64, 104, 144, 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