Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8532faf9a4319e847c00e70e949944479baf21f3de4b85666f3db8aca3316b2

Tx prefix hash: 3496d7a89b8cde9e465019c1d3baf70466d10f2c81aedbaf97f769cd9f4452fd
Tx public key: f0013a3e5a0b0516d9c009108dfa8cfc3334bfa3f67ba1aaf2e0c3d4f5cbbcec
Timestamp: 1733477418 Timestamp [UCT]: 2024-12-06 09:30:18 Age [y:d:h:m:s]: 00:138:16:36:43
Block: 1169191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98925 RingCT/type: yes/0
Extra: 01f0013a3e5a0b0516d9c009108dfa8cfc3334bfa3f67ba1aaf2e0c3d4f5cbbcec021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b20ec9470eeeb2654c2e8a27240121fce7a35f816557f44dc9a05b5f57df3fd 0.600000000000 1654906 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": 1169201, "vin": [ { "gen": { "height": 1169191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b20ec9470eeeb2654c2e8a27240121fce7a35f816557f44dc9a05b5f57df3fd" } } ], "extra": [ 1, 240, 1, 58, 62, 90, 11, 5, 22, 217, 192, 9, 16, 141, 250, 140, 252, 51, 52, 191, 163, 246, 123, 161, 170, 242, 224, 195, 212, 245, 203, 188, 236, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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