Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9d7beb37fa6c003e2de0df975bd8e7e6c91d0f0e04ed0a5e1165a6923c7ad52

Tx prefix hash: 4462f616ad80b8ce296efe5217ea36a4e313ec965c29353f4e2882713d527172
Tx public key: 469c11af087448c384f634f3f50462af22f123d9db29cb7fdc0dc7c8ce32bd57
Timestamp: 1714261659 Timestamp [UCT]: 2024-04-27 23:47:39 Age [y:d:h:m:s]: 01:193:20:10:28
Block: 1009976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397181 RingCT/type: yes/0
Extra: 01469c11af087448c384f634f3f50462af22f123d9db29cb7fdc0dc7c8ce32bd570211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3284a3d1324ee74ed12fc10fd771438fca1b150dd910e68f40c31dd5f9b1019 0.600000000000 1471798 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": 1009986, "vin": [ { "gen": { "height": 1009976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3284a3d1324ee74ed12fc10fd771438fca1b150dd910e68f40c31dd5f9b1019" } } ], "extra": [ 1, 70, 156, 17, 175, 8, 116, 72, 195, 132, 246, 52, 243, 245, 4, 98, 175, 34, 241, 35, 217, 219, 41, 203, 127, 220, 13, 199, 200, 206, 50, 189, 87, 2, 17, 0, 0, 0, 2, 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