Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8986b4bb4edcc2cd36d9f9503df66b59587ce5886d96336754b75fa9535ba11

Tx prefix hash: 8a2f5b5fb1661914ecfefd3141bae2f3884e8c97a368f1435aaf3d7f8b2d722a
Tx public key: 95d8e5b3108f6b2853567aa5d72265e0657a76bc28f96b9c469103195c2405fd
Timestamp: 1717356873 Timestamp [UCT]: 2024-06-02 19:34:33 Age [y:d:h:m:s]: 01:183:12:35:18
Block: 1035647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389777 RingCT/type: yes/0
Extra: 0195d8e5b3108f6b2853567aa5d72265e0657a76bc28f96b9c469103195c2405fd02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ddbef07c5359cb23fcaae039a4d9d1893f3cf298a6b59faac10dc37b753ff18 0.600000000000 1504168 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": 1035657, "vin": [ { "gen": { "height": 1035647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ddbef07c5359cb23fcaae039a4d9d1893f3cf298a6b59faac10dc37b753ff18" } } ], "extra": [ 1, 149, 216, 229, 179, 16, 143, 107, 40, 83, 86, 122, 165, 215, 34, 101, 224, 101, 122, 118, 188, 40, 249, 107, 156, 70, 145, 3, 25, 92, 36, 5, 253, 2, 17, 0, 0, 0, 2, 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