Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61a1ad789862d36e4bb2ed9dc8544792adc458703f6406319cf55e234806c257

Tx prefix hash: 0be0f2b3df4114c57623b49c19b1d368f97b2bdf0b57135e8ad3f4eeed33f042
Tx public key: 30673db5570d8b24654c86eb9cf3b8d8415a7ee165e60458430c99301f69d465
Timestamp: 1723517945 Timestamp [UCT]: 2024-08-13 02:59:05 Age [y:d:h:m:s]: 00:103:11:13:06
Block: 1086716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74022 RingCT/type: yes/0
Extra: 0130673db5570d8b24654c86eb9cf3b8d8415a7ee165e60458430c99301f69d465021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7da2bc7ea3fbed3e33410316cb611cb3d896329678e4f63fc4240ba2d9da6b13 0.600000000000 1561315 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": 1086726, "vin": [ { "gen": { "height": 1086716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7da2bc7ea3fbed3e33410316cb611cb3d896329678e4f63fc4240ba2d9da6b13" } } ], "extra": [ 1, 48, 103, 61, 181, 87, 13, 139, 36, 101, 76, 134, 235, 156, 243, 184, 216, 65, 90, 126, 225, 101, 230, 4, 88, 67, 12, 153, 48, 31, 105, 212, 101, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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