Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b862bd49b568400b40bdc4ecf9588aed15b152c787e323774d614f88f8984a78

Tx prefix hash: 2cc27eb721bbaafb42e969f7f496061c36dc94ac909d397ef1d22d65595024f3
Tx public key: 81f9ff48d629db78fb743fa8952e4286c7323712663c056aa5e5bccbe8d247aa
Timestamp: 1716814828 Timestamp [UCT]: 2024-05-27 13:00:28 Age [y:d:h:m:s]: 00:345:17:07:22
Block: 1031162 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247092 RingCT/type: yes/0
Extra: 0181f9ff48d629db78fb743fa8952e4286c7323712663c056aa5e5bccbe8d247aa02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9bc7487591fcd4e1a8598eee2ed5fe41163bc9e012a6a1d040b039eb2d8f025 0.600000000000 1499541 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": 1031172, "vin": [ { "gen": { "height": 1031162 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9bc7487591fcd4e1a8598eee2ed5fe41163bc9e012a6a1d040b039eb2d8f025" } } ], "extra": [ 1, 129, 249, 255, 72, 214, 41, 219, 120, 251, 116, 63, 168, 149, 46, 66, 134, 199, 50, 55, 18, 102, 60, 5, 106, 165, 229, 188, 203, 232, 210, 71, 170, 2, 17, 0, 0, 0, 4, 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