Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 900225902f288f1a1e4e41ad2d2b2c793986350be15063347730158714d9f18f

Tx prefix hash: d5086a576cf658fbdf745c82f9d0f21693593d606a2b09cf598d25ac93b57c8c
Tx public key: 44a1490b0c5d41fe2f109fdc61ff4d582edc93e9ed8cb31557007edd4e67fbe3
Timestamp: 1700498007 Timestamp [UCT]: 2023-11-20 16:33:27 Age [y:d:h:m:s]: 01:141:05:54:45
Block: 895870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362120 RingCT/type: yes/0
Extra: 0144a1490b0c5d41fe2f109fdc61ff4d582edc93e9ed8cb31557007edd4e67fbe30211000000054b8f5122000000000000000000

1 output(s) for total of 0.660101601000 dcy

stealth address amount amount idx
00: f89f74677599892c01e10230e1fbb5a2893dca0f141e1471b7b95088281c08cf 0.660101601000 1352117 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": 895880, "vin": [ { "gen": { "height": 895870 } } ], "vout": [ { "amount": 660101601, "target": { "key": "f89f74677599892c01e10230e1fbb5a2893dca0f141e1471b7b95088281c08cf" } } ], "extra": [ 1, 68, 161, 73, 11, 12, 93, 65, 254, 47, 16, 159, 220, 97, 255, 77, 88, 46, 220, 147, 233, 237, 140, 179, 21, 87, 0, 126, 221, 78, 103, 251, 227, 2, 17, 0, 0, 0, 5, 75, 143, 81, 34, 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