Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d404940b94bc113a2f7658780a9f17c9769af67563c136e8d2ebb906566e4f5

Tx prefix hash: ea0a9d5bf9747941384645eb6c46e4c5c7a7ce779e4d10ed08f0289b201c43a3
Tx public key: f6ddf83547ea2d436f97ea990744b50a6414c2fba84bc0de0a4e5564379c12ba
Timestamp: 1706439617 Timestamp [UCT]: 2024-01-28 11:00:17 Age [y:d:h:m:s]: 01:281:02:02:51
Block: 945110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459690 RingCT/type: yes/0
Extra: 01f6ddf83547ea2d436f97ea990744b50a6414c2fba84bc0de0a4e5564379c12ba02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fe9e4661ef0e1561c9a9ca572360e5fd9cab6a7ba5e1e10af6370b6938b6e5a 0.600000000000 1403420 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": 945120, "vin": [ { "gen": { "height": 945110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fe9e4661ef0e1561c9a9ca572360e5fd9cab6a7ba5e1e10af6370b6938b6e5a" } } ], "extra": [ 1, 246, 221, 248, 53, 71, 234, 45, 67, 111, 151, 234, 153, 7, 68, 181, 10, 100, 20, 194, 251, 168, 75, 192, 222, 10, 78, 85, 100, 55, 156, 18, 186, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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