Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d116568b6e3822995d6d4ac5c5dbf2d94ac8b2c9ba1b9d832c020750fa8042aa

Tx prefix hash: 2a3d48747862e951a83793cf714b9422c74ce75104939c6963fcd2b1b07af0e1
Tx public key: bfdc528196a86d590ee1c93c65d2b3632079b8b422fc82949871a6a09b014cad
Timestamp: 1748771440 Timestamp [UCT]: 2025-06-01 09:50:40 Age [y:d:h:m:s]: 00:164:00:00:56
Block: 1295546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114886 RingCT/type: yes/0
Extra: 01bfdc528196a86d590ee1c93c65d2b3632079b8b422fc82949871a6a09b014cad021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a45222091ec9a99bb562a9f4b8fa3d14c394127baab96314b2b2cdd17aa96eb 0.600000000000 1783049 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": 1295556, "vin": [ { "gen": { "height": 1295546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a45222091ec9a99bb562a9f4b8fa3d14c394127baab96314b2b2cdd17aa96eb" } } ], "extra": [ 1, 191, 220, 82, 129, 150, 168, 109, 89, 14, 225, 201, 60, 101, 210, 179, 99, 32, 121, 184, 180, 34, 252, 130, 148, 152, 113, 166, 160, 155, 1, 76, 173, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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