Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ef1d67af2034b99c6d56371f3a14689f7f270b43a1cf5758570b78d6b267c21

Tx prefix hash: dc27d1b097c7850e747444cc4ab58528042e4cf5f9fc9ced9b35fd4904a0752a
Tx public key: c396b69e064857897d581f234aad616d0f6edea21463ccf61c91a6e88253548b
Timestamp: 1705373128 Timestamp [UCT]: 2024-01-16 02:45:28 Age [y:d:h:m:s]: 01:043:00:28:41
Block: 936268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291820 RingCT/type: yes/0
Extra: 01c396b69e064857897d581f234aad616d0f6edea21463ccf61c91a6e88253548b0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 493977d94422b50e7c2f0dce17775c7c928e38a9ac1bd64094d3116988253a7c 0.600000000000 1394292 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": 936278, "vin": [ { "gen": { "height": 936268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "493977d94422b50e7c2f0dce17775c7c928e38a9ac1bd64094d3116988253a7c" } } ], "extra": [ 1, 195, 150, 182, 158, 6, 72, 87, 137, 125, 88, 31, 35, 74, 173, 97, 109, 15, 110, 222, 162, 20, 99, 204, 246, 28, 145, 166, 232, 130, 83, 84, 139, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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