Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da636a4caa176dffeb4de905c432cc5a3011b93b04ac86a966c114dc33d4317d

Tx prefix hash: e482b4faf6e15c83367196702fd0813a8ee1caab1086cb6c7149a2fe99c061d2
Tx public key: 965e935fec3b6b02de88858ac33f80cbc443f7158f5c20f87a8135add32de3a9
Timestamp: 1713891728 Timestamp [UCT]: 2024-04-23 17:02:08 Age [y:d:h:m:s]: 01:013:21:01:52
Block: 1006913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270870 RingCT/type: yes/0
Extra: 01965e935fec3b6b02de88858ac33f80cbc443f7158f5c20f87a8135add32de3a90211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c94e7e08f0c3fbcb4731b18fe38cc3e62a28f5e40c14ad421968d7504ae81be 0.600000000000 1468099 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": 1006923, "vin": [ { "gen": { "height": 1006913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c94e7e08f0c3fbcb4731b18fe38cc3e62a28f5e40c14ad421968d7504ae81be" } } ], "extra": [ 1, 150, 94, 147, 95, 236, 59, 107, 2, 222, 136, 133, 138, 195, 63, 128, 203, 196, 67, 247, 21, 143, 92, 32, 248, 122, 129, 53, 173, 211, 45, 227, 169, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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