Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6108b71c42142b49c166203568c8167600d470f06f1f0620c86891807bbcd3e3

Tx prefix hash: 4dd2313a70d53d2fd971a9d82f847d31251c52a35601c1c82baa5e4267575614
Tx public key: e87083e6c85c82d60f03e3f809c97be8727e4058800921f37a6c999e2d6e1281
Timestamp: 1736766397 Timestamp [UCT]: 2025-01-13 11:06:37 Age [y:d:h:m:s]: 00:063:22:55:29
Block: 1196414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45494 RingCT/type: yes/0
Extra: 01e87083e6c85c82d60f03e3f809c97be8727e4058800921f37a6c999e2d6e1281021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ff12e9aea7d5393a2ec7307cff46cfa4fb470e13410b0c9b7cbbe343f6aaf1e 0.600000000000 1683013 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": 1196424, "vin": [ { "gen": { "height": 1196414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ff12e9aea7d5393a2ec7307cff46cfa4fb470e13410b0c9b7cbbe343f6aaf1e" } } ], "extra": [ 1, 232, 112, 131, 230, 200, 92, 130, 214, 15, 3, 227, 248, 9, 201, 123, 232, 114, 126, 64, 88, 128, 9, 33, 243, 122, 108, 153, 158, 45, 110, 18, 129, 2, 17, 0, 0, 0, 6, 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