Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12030bf9076e3b2c7ecca6b3346b3fd3bf088aff10048150f9f369bcef77d45c

Tx prefix hash: 99d6f7416136b7740966103bd4ee8353450d233c33d3e6d358d6d407f96e3f16
Tx public key: be4a49d5b92faa40437e51acac3d3c8f7e66f47ad3c743650530e999be5df348
Timestamp: 1702278427 Timestamp [UCT]: 2023-12-11 07:07:07 Age [y:d:h:m:s]: 01:116:18:09:32
Block: 910632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344582 RingCT/type: yes/0
Extra: 01be4a49d5b92faa40437e51acac3d3c8f7e66f47ad3c743650530e999be5df3480211000000014b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b7f511d6e4eef972bdc71223a454e5d71c13adb1a3e76eede99c15f4b34d5e2 0.600000000000 1367793 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": 910642, "vin": [ { "gen": { "height": 910632 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b7f511d6e4eef972bdc71223a454e5d71c13adb1a3e76eede99c15f4b34d5e2" } } ], "extra": [ 1, 190, 74, 73, 213, 185, 47, 170, 64, 67, 126, 81, 172, 172, 61, 60, 143, 126, 102, 244, 122, 211, 199, 67, 101, 5, 48, 233, 153, 190, 93, 243, 72, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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