Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edfd6d832ee8409d07e40b25e7d8551e5c2c253349f123202533d5045f4af1b1

Tx prefix hash: e858bb9991486d03e60dd631dfd9c4d4a8c958b7a3b47c92d4be8e30523da089
Tx public key: ce18f45273684aaba687802bdff98e0da2055b217f6500e4f0fad9ffdb739a69
Timestamp: 1724745901 Timestamp [UCT]: 2024-08-27 08:05:01 Age [y:d:h:m:s]: 00:220:19:29:01
Block: 1096890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157678 RingCT/type: yes/0
Extra: 01ce18f45273684aaba687802bdff98e0da2055b217f6500e4f0fad9ffdb739a69021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5f12e1a3f84c85654dcf1f36eaf789b4d6b14e332397ad02b9541c7f4a08c55 0.600000000000 1572099 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": 1096900, "vin": [ { "gen": { "height": 1096890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5f12e1a3f84c85654dcf1f36eaf789b4d6b14e332397ad02b9541c7f4a08c55" } } ], "extra": [ 1, 206, 24, 244, 82, 115, 104, 74, 171, 166, 135, 128, 43, 223, 249, 142, 13, 162, 5, 91, 33, 127, 101, 0, 228, 240, 250, 217, 255, 219, 115, 154, 105, 2, 17, 0, 0, 0, 5, 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