Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f89a2fd7fd5985299e9b65705506119af0403db87384e73a3fcf8d5f4b0980f5

Tx prefix hash: d7d3151953eaca615d28599f5de1166a556bb73e0971c0d825a711d20b724256
Tx public key: a24035e5f5206b6f9177b435cab3d8df3477e8f1fa957a009b24ab6ddcb15dca
Timestamp: 1712875983 Timestamp [UCT]: 2024-04-11 22:53:03 Age [y:d:h:m:s]: 00:320:01:36:14
Block: 998469 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228819 RingCT/type: yes/0
Extra: 01a24035e5f5206b6f9177b435cab3d8df3477e8f1fa957a009b24ab6ddcb15dca0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e597c7e53acb835e55a8882898e7e90993f405c701f276befda76e612018635 0.600000000000 1458919 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": 998479, "vin": [ { "gen": { "height": 998469 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e597c7e53acb835e55a8882898e7e90993f405c701f276befda76e612018635" } } ], "extra": [ 1, 162, 64, 53, 229, 245, 32, 107, 111, 145, 119, 180, 53, 202, 179, 216, 223, 52, 119, 232, 241, 250, 149, 122, 0, 155, 36, 171, 109, 220, 177, 93, 202, 2, 17, 0, 0, 0, 6, 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