Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21edfcd069175a96c5b6487d5f9bb158a295bef28f7cc3c093787d2ab6e8ca43

Tx prefix hash: 0836119570cb38212466a0bf0a3f3655a65e144f5a86d39b2dec41f3032f898a
Tx public key: 5cf16f8526bd7bc15aafa902a7da257ebb3012014629d13e2b9fe7c5a54a7ec2
Timestamp: 1709462513 Timestamp [UCT]: 2024-03-03 10:41:53 Age [y:d:h:m:s]: 01:219:23:25:22
Block: 970194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415897 RingCT/type: yes/0
Extra: 015cf16f8526bd7bc15aafa902a7da257ebb3012014629d13e2b9fe7c5a54a7ec202110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df7004d3a6b43034a4c0fd05c2ac7441afcdaab33da52810326ddbfaa781e8cc 0.600000000000 1430043 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": 970204, "vin": [ { "gen": { "height": 970194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df7004d3a6b43034a4c0fd05c2ac7441afcdaab33da52810326ddbfaa781e8cc" } } ], "extra": [ 1, 92, 241, 111, 133, 38, 189, 123, 193, 90, 175, 169, 2, 167, 218, 37, 126, 187, 48, 18, 1, 70, 41, 209, 62, 43, 159, 231, 197, 165, 74, 126, 194, 2, 17, 0, 0, 0, 6, 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