Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86f1981b90fc978fa5b4edd1073b317cee77f48e695548e6477373d236fc71f9

Tx prefix hash: 7c64a19634bbd38e4f0a7332ffc545436035afcef912768fd2d4ae1988013e6c
Tx public key: 088d7f0b8f4f7ad48535161a8405a3216aa836034112b9aff8a653e465fdc8c7
Timestamp: 1687642643 Timestamp [UCT]: 2023-06-24 21:37:23 Age [y:d:h:m:s]: 01:199:14:55:01
Block: 789557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404042 RingCT/type: yes/0
Extra: 01088d7f0b8f4f7ad48535161a8405a3216aa836034112b9aff8a653e465fdc8c7021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.485491063000 dcy

stealth address amount amount idx
00: f8950fe522b574f6cd8d110074da94e1e10f959571eceb4458f8def655871315 1.485491063000 1239790 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": 789567, "vin": [ { "gen": { "height": 789557 } } ], "vout": [ { "amount": 1485491063, "target": { "key": "f8950fe522b574f6cd8d110074da94e1e10f959571eceb4458f8def655871315" } } ], "extra": [ 1, 8, 141, 127, 11, 143, 79, 122, 212, 133, 53, 22, 26, 132, 5, 163, 33, 106, 168, 54, 3, 65, 18, 185, 175, 248, 166, 83, 228, 101, 253, 200, 199, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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