Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ca2677fe352929e57b8f60f23d5b89327af9621521f02724967526ae43c249a

Tx prefix hash: 63d0f9edd27cdae1d74514ede0033f7a22e1f4075352dd35a0a55ecbb58c0715
Tx public key: 076b6ee820f118706f325a47333c5a9e509db8822dcd156b2394da1f7168fd3b
Timestamp: 1722374453 Timestamp [UCT]: 2024-07-30 21:20:53 Age [y:d:h:m:s]: 01:103:03:22:57
Block: 1077236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332210 RingCT/type: yes/0
Extra: 01076b6ee820f118706f325a47333c5a9e509db8822dcd156b2394da1f7168fd3b021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d528ae255b1cabe9ecef9d5ca6858bcdbdb4fe748ad900988745b946bc29c4e 0.600000000000 1549783 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": 1077246, "vin": [ { "gen": { "height": 1077236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d528ae255b1cabe9ecef9d5ca6858bcdbdb4fe748ad900988745b946bc29c4e" } } ], "extra": [ 1, 7, 107, 110, 232, 32, 241, 24, 112, 111, 50, 90, 71, 51, 60, 90, 158, 80, 157, 184, 130, 45, 205, 21, 107, 35, 148, 218, 31, 113, 104, 253, 59, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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