Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3298d1befdcd9f2609eb1e60d7200929e271cba3d24a094669e999ea3c007301

Tx prefix hash: 02d5872ad33128bab97b11599ba29e1b32eb39233ccb1118ac1a708db1d3c4b7
Tx public key: 714d4a1a8d30a87372c7209e6ce0bfd88fbac2a9e803c58f264be540b16a9b81
Timestamp: 1722047903 Timestamp [UCT]: 2024-07-27 02:38:23 Age [y:d:h:m:s]: 00:258:20:16:03
Block: 1074531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184917 RingCT/type: yes/0
Extra: 01714d4a1a8d30a87372c7209e6ce0bfd88fbac2a9e803c58f264be540b16a9b81021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e838de4820b92d48716a9134cff19ec3fc62469b88b4d370b1ae12da1fb53168 0.600000000000 1547044 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": 1074541, "vin": [ { "gen": { "height": 1074531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e838de4820b92d48716a9134cff19ec3fc62469b88b4d370b1ae12da1fb53168" } } ], "extra": [ 1, 113, 77, 74, 26, 141, 48, 168, 115, 114, 199, 32, 158, 108, 224, 191, 216, 143, 186, 194, 169, 232, 3, 197, 143, 38, 75, 229, 64, 177, 106, 155, 129, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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