Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d5034cc3a14aae0f7d6714848f5de477984a367bce3d4f6620366532d8d00d6

Tx prefix hash: eff959ac72e317cdcc4009abebb9ce45c75a21f94c84993d91b888dd77d2a5f7
Tx public key: aef98e9c2e08e1a5d21d7192822704c7cba6214a2c426c5939ee6231e87bab21
Timestamp: 1705831367 Timestamp [UCT]: 2024-01-21 10:02:47 Age [y:d:h:m:s]: 01:123:16:11:17
Block: 940058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349543 RingCT/type: yes/0
Extra: 01aef98e9c2e08e1a5d21d7192822704c7cba6214a2c426c5939ee6231e87bab210211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93d7105beb59ec9bf324b8e7b7ab49c5aeb2b2ba701a4a3e7fa210590299fdd5 0.600000000000 1398192 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": 940068, "vin": [ { "gen": { "height": 940058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93d7105beb59ec9bf324b8e7b7ab49c5aeb2b2ba701a4a3e7fa210590299fdd5" } } ], "extra": [ 1, 174, 249, 142, 156, 46, 8, 225, 165, 210, 29, 113, 146, 130, 39, 4, 199, 203, 166, 33, 74, 44, 66, 108, 89, 57, 238, 98, 49, 232, 123, 171, 33, 2, 17, 0, 0, 0, 1, 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