Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6886a9d073b14828a94adbac13446e8bfb3864e6c4c236eb3abdfee8e063b8ce

Tx prefix hash: 2e694a270cf05a706a7c5ef0440c3da56ba8d49f41edf5919544b49e5699d994
Tx public key: b41a70e957cef57294d14439a269b3b56cc0ae73617737a9e9c6eb3703e357e8
Timestamp: 1763824206 Timestamp [UCT]: 2025-11-22 15:10:06 Age [y:d:h:m:s]: 00:044:08:26:45
Block: 1417746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31785 RingCT/type: yes/0
Extra: 01b41a70e957cef57294d14439a269b3b56cc0ae73617737a9e9c6eb3703e357e8021100000001fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b671110b47adfe577ff78f0346a8190b4cc1b0fd472ee67ee500eb677d2ed1c 0.600000000000 1906273 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": 1417756, "vin": [ { "gen": { "height": 1417746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b671110b47adfe577ff78f0346a8190b4cc1b0fd472ee67ee500eb677d2ed1c" } } ], "extra": [ 1, 180, 26, 112, 233, 87, 206, 245, 114, 148, 209, 68, 57, 162, 105, 179, 181, 108, 192, 174, 115, 97, 119, 55, 169, 233, 198, 235, 55, 3, 227, 87, 232, 2, 17, 0, 0, 0, 1, 251, 143, 208, 137, 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