Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 630c782a10a8b35dad59b0094743a802d64f08fe0812b303320eb4e854f87015

Tx prefix hash: d74f16e13b9826b783b579c7cf5446736519fb69d64e017edc3e7690dd8b5041
Tx public key: 440efd59a19df0e59a162a715f4cb3abf81b8f9723684922d414ab81983e4ac3
Timestamp: 1724638159 Timestamp [UCT]: 2024-08-26 02:09:19 Age [y:d:h:m:s]: 00:224:02:33:18
Block: 1095999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160025 RingCT/type: yes/0
Extra: 01440efd59a19df0e59a162a715f4cb3abf81b8f9723684922d414ab81983e4ac302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72f3d0eee76b991a37f8094fcda28797c9861f08d43d8161d501bbdb96d6f76c 0.600000000000 1571186 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": 1096009, "vin": [ { "gen": { "height": 1095999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72f3d0eee76b991a37f8094fcda28797c9861f08d43d8161d501bbdb96d6f76c" } } ], "extra": [ 1, 68, 14, 253, 89, 161, 157, 240, 229, 154, 22, 42, 113, 95, 76, 179, 171, 248, 27, 143, 151, 35, 104, 73, 34, 212, 20, 171, 129, 152, 62, 74, 195, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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