Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0b906b6c4b140401ad713414da40a270e50a4c8c8fbf88ba21aad4d264e867e

Tx prefix hash: 454d5b51cc848654a2de87490ebf9a4a56a92c87bf8828cabcaf24523c993f3e
Tx public key: 4856261a4ee182f6956aed40175b26e41c624fc73444da6ce36ff604356c715a
Timestamp: 1698026273 Timestamp [UCT]: 2023-10-23 01:57:53 Age [y:d:h:m:s]: 01:189:08:09:19
Block: 875590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396357 RingCT/type: yes/0
Extra: 014856261a4ee182f6956aed40175b26e41c624fc73444da6ce36ff604356c715a02110000000433af99f4000000000000000000

1 output(s) for total of 0.770560734000 dcy

stealth address amount amount idx
00: 9667f0c1e175bfb4d7e326e8dfd75807088292a02098ea6c49204029eaec7e7b 0.770560734000 1330852 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": 875600, "vin": [ { "gen": { "height": 875590 } } ], "vout": [ { "amount": 770560734, "target": { "key": "9667f0c1e175bfb4d7e326e8dfd75807088292a02098ea6c49204029eaec7e7b" } } ], "extra": [ 1, 72, 86, 38, 26, 78, 225, 130, 246, 149, 106, 237, 64, 23, 91, 38, 228, 28, 98, 79, 199, 52, 68, 218, 108, 227, 111, 246, 4, 53, 108, 113, 90, 2, 17, 0, 0, 0, 4, 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