Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2865bae7cb990633cf971a0ea682d82817e947a0ab4fc05103a40c7ba573a7fc

Tx prefix hash: 7324ef46d3b8f1628a99ef4a80c447ea40a372680853a5ac9ad3bd8a969ef731
Tx public key: 0f5c294856d06a3195027a42bfa0286e32137e87da43b83c1a72b00b3d5275b4
Timestamp: 1714254203 Timestamp [UCT]: 2024-04-27 21:43:23 Age [y:d:h:m:s]: 01:186:21:01:32
Block: 1009915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392201 RingCT/type: yes/0
Extra: 010f5c294856d06a3195027a42bfa0286e32137e87da43b83c1a72b00b3d5275b402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12d2d3816ffbf4abce670609c126a6e308918d3e5e845bdd816c8e36d3858821 0.600000000000 1471721 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": 1009925, "vin": [ { "gen": { "height": 1009915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12d2d3816ffbf4abce670609c126a6e308918d3e5e845bdd816c8e36d3858821" } } ], "extra": [ 1, 15, 92, 41, 72, 86, 208, 106, 49, 149, 2, 122, 66, 191, 160, 40, 110, 50, 19, 126, 135, 218, 67, 184, 60, 26, 114, 176, 11, 61, 82, 117, 180, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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