Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3575b665f65a2eec8323acd6216c3fe6e51c5765b21da3ad29b89b276eec6f4

Tx prefix hash: 425d49490c62489e37b424beb4aaa8c50d7699e2a88a71c6da5d75be4c5d1b52
Tx public key: f86fe3be699d227c4d3913df5f54353398da47cc86b1f10bc74743f3d0d98aff
Timestamp: 1581371146 Timestamp [UCT]: 2020-02-10 21:45:46 Age [y:d:h:m:s]: 05:031:05:48:51
Block: 62366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175054 RingCT/type: yes/0
Extra: 01f86fe3be699d227c4d3913df5f54353398da47cc86b1f10bc74743f3d0d98aff02111c45662500000000000000000000000000

1 output(s) for total of 381.378641572000 dcy

stealth address amount amount idx
00: 669444bcb04d9b683c0af695f937a62114f3267ece98fa44e77264cf7c77afe0 381.378641572000 115033 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": 62376, "vin": [ { "gen": { "height": 62366 } } ], "vout": [ { "amount": 381378641572, "target": { "key": "669444bcb04d9b683c0af695f937a62114f3267ece98fa44e77264cf7c77afe0" } } ], "extra": [ 1, 248, 111, 227, 190, 105, 157, 34, 124, 77, 57, 19, 223, 95, 84, 53, 51, 152, 218, 71, 204, 134, 177, 241, 11, 199, 71, 67, 243, 208, 217, 138, 255, 2, 17, 28, 69, 102, 37, 0, 0, 0, 0, 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