Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2fc92c201d2376e0b9353929166aee1f901896921b0a206ada9280fd27dc310

Tx prefix hash: 3e577eaec453094351ce7df4eed575a596c4b8728b280ba5347dcd1ba571ca89
Tx public key: af1c5af8e0fbe7d95004f97a082cbbadfb6f7017ef4f0a1370eac8c0460a7479
Timestamp: 1705287835 Timestamp [UCT]: 2024-01-15 03:03:55 Age [y:d:h:m:s]: 01:298:23:52:13
Block: 935551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 472521 RingCT/type: yes/0
Extra: 01af1c5af8e0fbe7d95004f97a082cbbadfb6f7017ef4f0a1370eac8c0460a74790211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 883bdb3c0100f40cfb563b8be2bbd7ad4b4e4ab66c5da30857125b16740e7c79 0.600000000000 1393567 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": 935561, "vin": [ { "gen": { "height": 935551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "883bdb3c0100f40cfb563b8be2bbd7ad4b4e4ab66c5da30857125b16740e7c79" } } ], "extra": [ 1, 175, 28, 90, 248, 224, 251, 231, 217, 80, 4, 249, 122, 8, 44, 187, 173, 251, 111, 112, 23, 239, 79, 10, 19, 112, 234, 200, 192, 70, 10, 116, 121, 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