Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d29e746de7032b6cbe4514df7a0b450eda48e267742e984cdd8d5701d3d17e8e

Tx prefix hash: 61c913c95552bd6013265e7a99d3552587353c0e0b1139b0fe0874b78897d182
Tx public key: 7afe8c971a360f1769076e6296e093b2b0385acd45e4a5d9dbe3c9605ce05b10
Timestamp: 1733706409 Timestamp [UCT]: 2024-12-09 01:06:49 Age [y:d:h:m:s]: 00:114:01:00:02
Block: 1171105 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81265 RingCT/type: yes/0
Extra: 017afe8c971a360f1769076e6296e093b2b0385acd45e4a5d9dbe3c9605ce05b10021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7de0b87b217085315b0f7b2d2f544ecdae2be576560909818bd8fc04233b44f3 0.600000000000 1656842 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": 1171115, "vin": [ { "gen": { "height": 1171105 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7de0b87b217085315b0f7b2d2f544ecdae2be576560909818bd8fc04233b44f3" } } ], "extra": [ 1, 122, 254, 140, 151, 26, 54, 15, 23, 105, 7, 110, 98, 150, 224, 147, 178, 176, 56, 90, 205, 69, 228, 165, 217, 219, 227, 201, 96, 92, 224, 91, 16, 2, 17, 0, 0, 0, 1, 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