Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 611f7dde4e61df6a8a0645b34d6a95f35e4b92edb6e5f3ac5831c211e1014827

Tx prefix hash: b89072c205bf7603dfc675310c04f25b531f04e87d6d4fae9a6f0c8725970104
Tx public key: 7c5475ba9d7b23af23fefd29b7a7c728cb61478be505a8dddf86b70bed48058e
Timestamp: 1726765418 Timestamp [UCT]: 2024-09-19 17:03:38 Age [y:d:h:m:s]: 00:066:01:47:54
Block: 1113638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 47235 RingCT/type: yes/0
Extra: 017c5475ba9d7b23af23fefd29b7a7c728cb61478be505a8dddf86b70bed48058e021100000003e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 31b63c2873c1e280229449b30bccf26970850466522827fa61532fd1762ea2e3 0.608000000000 1593381 of 0

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": 1113648, "vin": [ { "gen": { "height": 1113638 } } ], "vout": [ { "amount": 608000000, "target": { "key": "31b63c2873c1e280229449b30bccf26970850466522827fa61532fd1762ea2e3" } } ], "extra": [ 1, 124, 84, 117, 186, 157, 123, 35, 175, 35, 254, 253, 41, 183, 167, 199, 40, 203, 97, 71, 139, 229, 5, 168, 221, 223, 134, 183, 11, 237, 72, 5, 142, 2, 17, 0, 0, 0, 3, 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