Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3df41420a7b0a75754cbdf5b15636ebafe09be55c4c0a38798045c86668baf34

Tx prefix hash: eecf5ecf1dd37bc31a68df1ce8e6c480176fb8292a60783482bf9b8ecccb5c2d
Tx public key: b958e9f616e35302501e076c5caeeadb83acded12e0cf6e94218170b4204fde3
Timestamp: 1697341018 Timestamp [UCT]: 2023-10-15 03:36:58 Age [y:d:h:m:s]: 01:171:05:20:51
Block: 869900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383396 RingCT/type: yes/0
Extra: 01b958e9f616e35302501e076c5caeeadb83acded12e0cf6e94218170b4204fde302110000000633af99f4000000000000000000

1 output(s) for total of 0.804748572000 dcy

stealth address amount amount idx
00: f6a899aa4cfae04138892695639594c2a3cbb02e218af9fbba720884ecbb79b2 0.804748572000 1324765 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": 869910, "vin": [ { "gen": { "height": 869900 } } ], "vout": [ { "amount": 804748572, "target": { "key": "f6a899aa4cfae04138892695639594c2a3cbb02e218af9fbba720884ecbb79b2" } } ], "extra": [ 1, 185, 88, 233, 246, 22, 227, 83, 2, 80, 30, 7, 108, 92, 174, 234, 219, 131, 172, 222, 209, 46, 12, 246, 233, 66, 24, 23, 11, 66, 4, 253, 227, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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