Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a7aad087057c73b3a2463b6fb51a7a6edb5b6f024c35539a1cdfa6e98a8d3c3

Tx prefix hash: 072c2e9411a44ead57e0c81eeee2750166e1a5d2f9165d946156507070b3e2ea
Tx public key: 8122f327438b363d7bbb51e56e7747ff35408dd469491edb6a84c8567227f800
Timestamp: 1690869471 Timestamp [UCT]: 2023-08-01 05:57:51 Age [y:d:h:m:s]: 01:247:23:23:38
Block: 816317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438305 RingCT/type: yes/0
Extra: 018122f327438b363d7bbb51e56e7747ff35408dd469491edb6a84c8567227f80002110000000375e3f0e9000000000000000000

1 output(s) for total of 1.211164173000 dcy

stealth address amount amount idx
00: b0a720ab00654f76fdf2d2e6c1e7467818c1506d1268c6ab01c6047387fdfa2d 1.211164173000 1268152 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": 816327, "vin": [ { "gen": { "height": 816317 } } ], "vout": [ { "amount": 1211164173, "target": { "key": "b0a720ab00654f76fdf2d2e6c1e7467818c1506d1268c6ab01c6047387fdfa2d" } } ], "extra": [ 1, 129, 34, 243, 39, 67, 139, 54, 61, 123, 187, 81, 229, 110, 119, 71, 255, 53, 64, 141, 212, 105, 73, 30, 219, 106, 132, 200, 86, 114, 39, 248, 0, 2, 17, 0, 0, 0, 3, 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