Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9125d74876f53e6f83788ba28dc2db154408b91b2296f2cf8d2b9fb3e20048b7

Tx prefix hash: 7141bbb4e9bcb490ed53574333582bf2a046d21e49a2880e6a8695a5c8d00dd0
Tx public key: ee457b7c2dad2f286609e68009a6eb91aecf8a684c4b4117971f7f1beb3e2b45
Timestamp: 1699896422 Timestamp [UCT]: 2023-11-13 17:27:02 Age [y:d:h:m:s]: 01:352:23:39:52
Block: 890888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511178 RingCT/type: yes/0
Extra: 01ee457b7c2dad2f286609e68009a6eb91aecf8a684c4b4117971f7f1beb3e2b4502110000000975e3f0e9000000000000000000

1 output(s) for total of 0.685674862000 dcy

stealth address amount amount idx
00: 7457033a951cb95d7f5ab663ed5135488ff5fe84cfb57a77e16e57dc26935009 0.685674862000 1346919 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": 890898, "vin": [ { "gen": { "height": 890888 } } ], "vout": [ { "amount": 685674862, "target": { "key": "7457033a951cb95d7f5ab663ed5135488ff5fe84cfb57a77e16e57dc26935009" } } ], "extra": [ 1, 238, 69, 123, 124, 45, 173, 47, 40, 102, 9, 230, 128, 9, 166, 235, 145, 174, 207, 138, 104, 76, 75, 65, 23, 151, 31, 127, 27, 235, 62, 43, 69, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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