Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edb3e61f34a5603ff936a222ac8558c101e52b9fa6e0f3c8e293a9cf1ab7cc0f

Tx prefix hash: 7adedfbcdd6fe5adb488608415ffdad7ec9cb2c73942143c4e9ded597b187d60
Tx public key: 0e669f7fd7f60d3d46a207048f5f7b3869eeb8a863280bf0994a595a1fafab7a
Timestamp: 1716962688 Timestamp [UCT]: 2024-05-29 06:04:48 Age [y:d:h:m:s]: 00:300:02:22:47
Block: 1032383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214466 RingCT/type: yes/0
Extra: 010e669f7fd7f60d3d46a207048f5f7b3869eeb8a863280bf0994a595a1fafab7a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90f9da93dfc752c9122d60b34deab845a9a6360b31e6eb257722937062d6018a 0.600000000000 1500836 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": 1032393, "vin": [ { "gen": { "height": 1032383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90f9da93dfc752c9122d60b34deab845a9a6360b31e6eb257722937062d6018a" } } ], "extra": [ 1, 14, 102, 159, 127, 215, 246, 13, 61, 70, 162, 7, 4, 143, 95, 123, 56, 105, 238, 184, 168, 99, 40, 11, 240, 153, 74, 89, 90, 31, 175, 171, 122, 2, 17, 0, 0, 0, 3, 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