Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cae420372f48ccad48fad3748182741bf66cde1a632c83bac28dd8b4645300df

Tx prefix hash: 2e2580ad741ac503151eaa5bf73f91d11b31d2a1a16236836f19d0c321bd8b83
Tx public key: 7131fac5f8ba3444ae81d774f6bb4fb8f0e551db5598cc5e71f9b7f4ad94b719
Timestamp: 1718616984 Timestamp [UCT]: 2024-06-17 09:36:24 Age [y:d:h:m:s]: 00:332:04:51:49
Block: 1046088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237428 RingCT/type: yes/0
Extra: 017131fac5f8ba3444ae81d774f6bb4fb8f0e551db5598cc5e71f9b7f4ad94b7190211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b52da6ef323203b30fd6b0a2f580308392cf4e4a55f58be4ffb25dd6d354ff3e 0.600000000000 1515847 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": 1046098, "vin": [ { "gen": { "height": 1046088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b52da6ef323203b30fd6b0a2f580308392cf4e4a55f58be4ffb25dd6d354ff3e" } } ], "extra": [ 1, 113, 49, 250, 197, 248, 186, 52, 68, 174, 129, 215, 116, 246, 187, 79, 184, 240, 229, 81, 219, 85, 152, 204, 94, 113, 249, 183, 244, 173, 148, 183, 25, 2, 17, 0, 0, 0, 4, 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