Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd1a55103d50353f01005005a8bc9f9cda0798953d615fd33e6e46b3e0be50e0

Tx prefix hash: eb76d0fca09196913d5be61370d613f4239e3716e972bdf16345002613ca9c72
Tx public key: 0ad6361ecd32371b1fe76a2c688995d30aa27c2064f52c621f72559ea3a9189b
Timestamp: 1698381961 Timestamp [UCT]: 2023-10-27 04:46:01 Age [y:d:h:m:s]: 01:086:20:41:04
Block: 878551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323256 RingCT/type: yes/0
Extra: 010ad6361ecd32371b1fe76a2c688995d30aa27c2064f52c621f72559ea3a9189b02110000000233af99f4000000000000000000

1 output(s) for total of 0.753348361000 dcy

stealth address amount amount idx
00: d4fceba1ec8cef7151b13a4af78d8a080905d953360ca88cde3e90310a7c064b 0.753348361000 1334003 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": 878561, "vin": [ { "gen": { "height": 878551 } } ], "vout": [ { "amount": 753348361, "target": { "key": "d4fceba1ec8cef7151b13a4af78d8a080905d953360ca88cde3e90310a7c064b" } } ], "extra": [ 1, 10, 214, 54, 30, 205, 50, 55, 27, 31, 231, 106, 44, 104, 137, 149, 211, 10, 162, 124, 32, 100, 245, 44, 98, 31, 114, 85, 158, 163, 169, 24, 155, 2, 17, 0, 0, 0, 2, 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