Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc96ca75a85b411d205fb913fdf493dae1a08c5f628a575108147149aa20fc91

Tx prefix hash: acaa67f0119a0def68ff823058c75cfb6bb54eb8adba621071f8ec30dbed8bf0
Tx public key: a67cf6642d5b77cf8da10d887949a0d120a20c5b6c3a7cfb12f8785af0308bf4
Timestamp: 1711439140 Timestamp [UCT]: 2024-03-26 07:45:40 Age [y:d:h:m:s]: 00:339:17:35:45
Block: 986604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242855 RingCT/type: yes/0
Extra: 01a67cf6642d5b77cf8da10d887949a0d120a20c5b6c3a7cfb12f8785af0308bf40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b362a09b7f8f16269ff7eef032d3aaee7d1a923cc839b1e8d39d06020824ccf4 0.600000000000 1446835 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": 986614, "vin": [ { "gen": { "height": 986604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b362a09b7f8f16269ff7eef032d3aaee7d1a923cc839b1e8d39d06020824ccf4" } } ], "extra": [ 1, 166, 124, 246, 100, 45, 91, 119, 207, 141, 161, 13, 136, 121, 73, 160, 209, 32, 162, 12, 91, 108, 58, 124, 251, 18, 248, 120, 90, 240, 48, 139, 244, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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